home *** CD-ROM | disk | FTP | other *** search
- What's new with v3.0?
- -------------------------------------------------------------------------------
-
- Please note: Don't be misled by the "demo" tag on the shareware
- version of BBSkit! Just because it says "demo" doesn't mean it is
- crippleware. The "demo" version is only a subset of the registered package.
-
- Even if you don't register BBSkit, I'd love to hear your opinions
- about BBSkit. Drop me a note at home (my address is in ORDER.FRM) or leave
- me electronic mail:
-
- CompuServe: >INTERNET:sjmadsen@miavx1.acs.muohio.edu
- Internet: sjmadsen@miavx1.acs.muohio.edu
- BITNET: SJMADSEN@MIAVX1
-
- Inside v3.0 you will find...
-
- * Concurrent port support. It's been a while in coming, but you
- can finally use more than one serial port with BBSkit. Now you
- can open two ports (say, COM1 and COM2) and read and write to
- both of them without skipping a beat. All it requires is an
- extra parameter to the low-level procedures!
-
- * The assembly routines have been optimized for increased speed and
- reliability. The ReceiveBlock and SendBlock procedures have been
- added to improve throughput on any block-oriented receive or
- send operations.
-
- * New TCountdownTimer object and enhanced TTimer object. These
- perform countdown and stopwatch functions for your programs.
- TCountdownTimer is used by BBSkit for user time limits.
- TTimer has been changed to support multiple starts/stops without
- resetting the timer unless needed!
-
- * Virtual consoles and the use of MTASK now permit more than one
- console in your program. BBSkit handles writing the correct screen
- by itself. MTASK is also provided, which provides a sort of
- demand-driven multitasking to Turbo Pascal programs. Basically, it
- means you can create more than a single task, and each call to a
- certain procedure switches among them. Calling this procedure often
- will give a good illusion of multitasking. (BBSkit already has this
- sprinkled through the code, so you will have to do almost nothing to
- take advantage of this multithreading.)
-
- * Previously, the emulation templates (*.EMU) were provided separate
- and as a combined library (STD.EML). To save allocated disk space,
- the templates will only come in library form from now on. If you
- still want them in .EMU form you can register the kit and use the
- provided EmuMaker utility to extract them.
-
- * The procedure Movsw in the Util unit was changed to MoveWord to
- appear more like the System unit Move procedure. FillWord was
- added to provide word-storing functionality of FillChar.
-
- * There is now a CPU detection routine in the Util unit which acts
- sort of like the BP7 version, except I think it's a little more
- accurate (it reports '3' for a 386 instead of '2' and also
- distinguishes between an 8088 and an 8086).
-
- * The Date and Time functions in the Util unit now pay attention to
- the country information as set through DOS and return strings that
- make sense based on this information (Date returns DD-MM-YY for
- Europe, for example).
-
- Features which are denoted with (+) are available in the registered
- version only. (Hey, there's gotta be SOME incentive to register...) The
- only thing that begs explanation is the protocols. You still get Xmodem and
- the variations of it (CRC-16 and 1K blocks). Registered versions of the kit
- also remove that annoying pause for a key at the beginning of programs you
- write with BBSkit.
-
- In addition to these new features, some undocumented features that
- were causing some problems have been removed:
-
- * ComReadLn and ComReadLnWrap both had an annoying quality to them
- which essentially limited their input to one character or so.
- Fixed.
-
- * There was an off-by-one error in the ANSI part of DoGotoXY. Fixed.
-
- * Handshaking was completely overlooked in some parts of the assembly
- code. I never got any bug reports, but it's fixed anyway.
-
- * There was a minor bug in CommandLineValue from the Util unit. See
- the manual for details.
-
- * There was a nasty bug in 2.0: if you opened more than one comport
- during your program, when it tried to end itself, it would hang the
- machine. There was a problem with hooking ExitProc. Fixed.
-
- * There was a problem with ANSI codes for color which defined the
- high intensity part *before* the color itself. Result: no bright
- colors (BBSkit can get bright colors because it sets high intensity
- *after* the color.) This caused problems with programs such as
- TheDraw, which do it in the reverse order (high intensity, then
- color). Fixed.
-
- * There was a problem positioning using EmuGotoXY along the X axis
- for all emulation templates. Fixed.
-
- * The interrupt routines bombed easily at speeds greater than
- 19,200bps. They have been fixed and now work reliably up to
- 57,600bps. On a fast machine, even 115,200 shouldn't be a problem.
-
- * TypeFile forgot to close the files it opened. Fixed.
-
-